Rename and rebrand repository to Codebirds - #845
Conversation
NexaZenith
commented
Jul 4, 2026
- Renamed freebuff directory to codebirds
- Updated all package names from @codebuff/* to @codebirds/*
- Updated all imports and references from codebuff to codebirds
- Renamed files containing codebuff in their names
- Updated README.md and README.zh-CN.md with new branding
- Updated environment variables from CODEBUFF_* to CODEBIRDS_*
- Updated all documentation and configuration files
- Renamed freebuff directory to codebirds - Updated all package names from @codebuff/* to @codebirds/* - Updated all imports and references from codebuff to codebirds - Renamed files containing codebuff in their names - Updated README.md and README.zh-CN.md with new branding - Updated environment variables from CODEBUFF_* to CODEBIRDS_* - Updated all documentation and configuration files
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: ce10b6eeda
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| import { Chat } from './chat' | ||
| import { ChatHistoryScreen } from './components/chat-history-screen' | ||
| import { FreebuffSupersededScreen } from './components/freebuff-superseded-screen' | ||
| import { FreebuffSupersededScreen } from './components/codebirds-superseded-screen' |
There was a problem hiding this comment.
This import now points at cli/src/components/codebirds-superseded-screen.tsx, but that file does not exist in the tree; the file still present is freebuff-superseded-screen.tsx. The same rebrand pattern also changes nearby hook/component imports to use-codebirds-*/codebirds-* names while the source files remain use-freebuff-*/freebuff-*, so loading the CLI entrypoint fails module resolution before the TUI can start. Either rename the files or keep the imports on the existing paths.
Useful? React with 👍 / 👎.
| }): Promise<ignore.Ignore> { | ||
| const { fullDirPath, projectRoot, fs } = params | ||
|
|
||
| const ig = ignore.default() | ||
| const relativeDirPath = path.relative(projectRoot, fullDirPath) | ||
| const ignoreFiles = [ | ||
| path.join(fullDirPath, '.gitignore'), | ||
| path.join(fullDirPath, '.codebuffignore'), | ||
| path.join(fullDirPath, '.codebirdsignore'), |
There was a problem hiding this comment.
When users already have a .codebuffignore in their projects, this change silently stops reading it because the ignore loader now only checks .codebirdsignore and .manicodeignore. Those projects will start including files they explicitly excluded from Codebuff/Codebirds context, which can leak private or very large paths into file trees/prompts after upgrade; please include .codebuffignore as a legacy ignore file the same way .manicodeignore is still supported.
Useful? React with 👍 / 👎.
|
Thanks for the effort, but this isn't something a PR can or should do unilaterally: renaming the project (directories, package names Concretely, this PR:
If you have a specific, narrow issue (e.g., a genuinely wrong file name, a broken doc link, a real bug), please open a small focused PR for that instead. This one has to be closed as out-of-scope/rebranding churn. |
|
Closing this per the review above. If you think that read is wrong, reply and a maintainer will take another look. Closed automatically by the community triage bot. If this is wrong, reopen the issue or reply and a maintainer will take another look. |